This problem typically occurs on computers with pre-installed Windows 7 or Windows Server 2008 R2 operating system, such as notebooks. It is caused by the invalid junction point at <SystemDrive>:\ProgramData\Documents, which resolves to a non-existing location instead of the Public Documents folder. For more information on junction points, see the Junction Points article on MSDN:
http://msdn.microsoft.com/en-us/library/bb968829.aspx
To check if the junction point is correct:
-
Open an elevated Command Prompt with administrator privileges:
-
Click Start and type
cmd.exeinto the Search box. -
Right-click cmd.exe in the search results and click Run as administrator.
-
-
Type the following command into the Command Prompt and press Enter:
dir C:\ProgramData /al(If your operating system is installed on a drive other than C:, change the drive letter accordingly.)
-
Examine the destination path of the Documents junction point:
-
If it specifies [C:\Users\Public\Documents] (assuming that your system drive is C:), the junction point is correct.
-
If it starts with an incorrect drive letter, for example, [S:\Users\Public\Documents], the junction point is broken.
-
-
To fix an incorrect junction point, run the following commands in the Command Prompt:
rd C:\ProgramData\Documents
mklink /j C:\ProgramData\Documents C:\Users\Public\Documents(If your operating system is installed on a drive other than C:, change the drive letter accordingly.)
After correcting the junction point, run the LoadComplete installation program in the Repair mode to install the sample applications and test projects.
We also recommend that you contact your computer supplier on the issue with junction points as they were set incorrectly during the operating system installation.